System and method for controlling movable barrier operation at a secured premises

ABSTRACT

In one aspect, a method is provided for controlling access to a facility including a movable barrier and a plurality of loading docks. The method includes receiving, from a user device associated with a vehicle, a check-in communication that includes a check-in identifier. The method includes receiving a verification communication that verifies a presence of the vehicle relative to a sensor associated with the movable barrier. The method further includes causing a movable barrier operator associated with the movable barrier to move the movable barrier between closed and open positions in response to the check-in identifier indicating authorization to access the facility and in response to receiving the verification communication. Further, the method includes selecting a particular loading dock from the plurality of loading docks and communicating a loading dock identification representative of the particular loading dock to the user device to direct the vehicle to the particular loading dock.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent App. No.62/914,745, filed Oct. 14, 2019, and claims the benefit of U.S.Provisional Patent App. No. 62/900,569, filed Sep. 15, 2019, which areall hereby incorporated by reference herein in their entireties.

FIELD

The present disclosure relates to controlling movable barrier operators,and more particularly, to controlling access to a facility having amovable barrier and a plurality of loading docks.

BACKGROUND

Movable barrier operators of various kinds are used to control theopening and closing of gates, doors, and other barriers that permitaccess to secured premises and/or enclosed spaces. Example movablebarrier operators include gate operators, rolling shutter operators,garage door operators, and the like.

Commercial and industrial facilities may have a fence or wall around thefacility and one or more gates or other barriers for controlling accessto the facility. Examples of such facilities include warehouses,factories, logistic centers, and assembly plants. Typically, when avehicle such as a semi-trailer truck arrives at such a facility, thevehicle operator must “check in” at a gate before the vehicle ispermitted to enter the facility. If the vehicle is authorized, anemployee at the gate will open the gate. This check-in process may betime consuming, resulting in increased vehicle idle time at theperimeter of the facility. Increased idle time reduces the efficiency ofboth the vehicle operator and the facility.

Upon check-in, a vehicle may be directed by the employee at the gate toa loading dock to load or unload freight. In some instances, the loadingor unloading of freight may be delayed upon arrival of the vehicle atthe loading dock. Such a delay may occur, for example, when facilitypersonnel are not available at the loading dock at the time the vehiclearrives at the loading dock. Thus, conventional approaches for logisticsat a facility may result in idle time of vehicles at the gate of thefacility as well as detention time and/or dwell time within thefacility. As can be appreciated, facility inefficiencies such as theforegoing-mentioned idle time, detention time and dwell time may resultin lost time to carriers (or vehicle drivers/operators) and additionalcost to shippers or receivers.

Another problem with conventional approaches is that there is often noway for a trucking company to independently confirm the time a truck hasarrived or departed from a facility. The employee of the facility suchas a spotter or a guard at the entry/exit gate may keep a paper recordof the trucks entering and exiting the facility, but the paper recordmay be lost or tampered with. A related problem encountered by truckingcompanies is that the contents of trailers are often tracked using paperbills of lading, which create delays and difficulties in reconciliationincluding freight tracking and billing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example schematic diagram showing a movable barrieroperator for controlling access to a facility, dock door operators forcontrolling access to loading docks of the facility, and a remote servercomputer for controlling the movable barrier operator and the dock dooroperator.

FIG. 2 is an example block diagram of the movable barrier operator ofFIG. 1.

FIG. 3 is an example block diagram of the remote server computer of FIG.1.

FIG. 4 is an example block diagram of the user device of FIG. 1.

FIG. 5 is a schematic diagram showing an example loading dock of thefacility of FIG. 1.

FIG. 6 is a flow chart of an example method that includes controllingaccess at the facility of FIG. 1.

Embodiments of the present disclosure are described herein. It is to beunderstood, however, that the disclosed embodiments are merely examplesand other embodiments may take various and alternative forms. Thefigures are not necessarily to scale; some features could be exaggeratedor minimized to show details of particular components. Therefore,specific structural and functional details disclosed herein are not tobe interpreted as limiting, but merely as a representative basis forteaching one skilled in the art to variously employ the presentinvention. As those of ordinary skill in the art will understand,various features illustrated and described with reference to any one ofthe figures may be combined with features illustrated in one or moreother figures to produce embodiments that are not explicitly illustratedor described. The combinations of features illustrated providerepresentative embodiments for typical applications. Variouscombinations and modifications of the features consistent with theteachings of this disclosure, however, could be employed for particularapplications or implementations.

DETAILED DESCRIPTION

In one aspect of the present disclosure, a system is provided forcontrolling access to a facility that includes a movable barrier and aplurality of loading docks. The system includes a remote computer, suchas a remote server computer, that may be configured to communicatecontrol commands to a movable barrier operator to effect movement of themovable barrier. The remote server computer may further be configured tocommunicate control commands to a dock door operator to effect movementof an associated loading dock door.

More particularly, the remote server computer may perform at least aportion of a check-in process upon a vehicle arriving at a movablebarrier of the facility. The check-in process may include the remoteserver computer receiving a check-in communication from a user deviceassociated with the vehicle. The check-in process further includesverifying a presence of the vehicle at the movable barrier; for example,as detected by one or more sensors proximate the movable barrier. Theremote server computer receives a verification communication indicatingthe presence of the vehicle at the movable barrier upon the one or moresensors detecting the vehicle. After receiving both the check-incommunication and the verification communication indicating the presenceof the vehicle, the remote server computer communicates a controlcommand to the movable barrier operator and/or the user device to permitmovement (e.g., opening) of the movable barrier. As such, the vehicle isgranted access to the secured premises of the facility.

In one approach, the remote server computer may select a particularloading dock from the plurality of loading docks. The remote servercomputer may further communicate a loading dock identificationrepresentative of the particular loading dock to the user device todirect the vehicle to the particular loading dock. In an optionalapproach, the remote server computer may cause the particular loadingdock to configure at least one loading dock component to facilitatereceiving the vehicle.

The remote server computer may also perform at least a portion of a dockarrival process upon the vehicle arriving at the particular loading dockarea. The dock arrival process may include the remote server computerreceiving a dock arrival communication from the user device. The dockarrival process further includes verifying a presence of the vehicle atthe particular loading dock area; for example, as detected by one ormore sensors disposed proximate the loading dock. The remote servercomputer receives a dock verification communication indicating thepresence or absence of the vehicle at the particular loading dock areaupon the one or more sensors detecting the vehicle. Upon receiving boththe dock arrival communication and the dock verification communicationindicating the presence of the vehicle, the remote server computertransmits a control command to a dock door operator to effect movement(e.g., opening) of the dock door. As such, the vehicle is granted accessto an interior of the loading dock.

The remote sever computer may also perform at least a portion of a checkout process that includes initiating billing upon the vehicle beingpartially or completely unloaded at the facility. The check out processmay also include the remote server receiving bill of lading informationif the vehicle has been loaded with new freight. The check out processmay involve the user device automatically, or in response to user input,communicating a notification that the vehicle is in route to asubsequent delivery or that the driver is available to be assigned to anew load location. The check out process may also include the remoteserver receiving information indicative of operational efficiency thatmay in certain instances represent charges/fees directed to theshipping/receiving facility and/or to the carrier or vehicle operator;e.g., the duration of the time from the user device causing opening ofthe movable barrier until the vehicle arrives at the dock, the durationof time the vehicle is at the dock which if greater than a predeterminedduration may factor into a detention fee to be paid by the facility tothe carrier or vehicle operator, and/or the duration of time the vehicletakes to check out at the gate after unloading at the dock.

Referring now to FIG. 1, a facility 10 includes a perimeter barrier 12that inhibits access to a secured premises 16. The facility 10 may be,for example, a warehouse, a shipping facility, an assembly plant, andthe like. The facility 10 may include plurality of loading docks 14located within the secured premises 16 of the facility 10. A vehicle 20,which may be a tractor-trailer, flatbed truck, or cargo van as someexamples, accesses the loading docks 14 via a movable barrier 32, suchas a gate, of the perimeter barrier 12 to load or unload freight 22 atthe loading docks 14. As discussed in greater detail below, a user(e.g., the operator) of the vehicle 20 may operate one or more userdevices 24 upon arrival at the perimeter barrier 12 to initiate openingof the movable barrier 32, and may operate the user device 24 uponarrival at a loading dock 14 to initiate opening of a movable barrier ofthe loading dock 14, such as a loading dock door 204.

The perimeter barrier 12 shown in FIG. 1 is in the form of a chain linkfence having fixed barrier portions 30 and the movable barrier 32 thatshifts relative to the fixed barrier portions 30. The movable barrier 32shown in FIG. 1 may include rollers that travel along a track as themovable barrier 32 is shifted relative to the fixed barrier portions 30.In other embodiments, the movable barrier 32 may be include a swinginggate or door, a sectional garage door or one-piece “California” garagedoor, a roller door, a movable arm, tire spikes, or another suitablebarrier for controlling access to the secured premises 16.

The facility 10 includes a system 5 for selectively permitting access tothe facility 10. The system 5 includes a movable barrier operator 40,such as a gate operator, operatively connected to the movable barrier 32to move the movable barrier 32 between a closed position and an openposition. The movable barrier operator 40 may include or be incommunication with an access control apparatus such as a telephone entrysystem-like panel that is configured to manage or control operation ofthe movable barrier operator 40. The access control apparatus may beconfigured with audio and/or video communication hardware such as amicrophone, speaker, and/or camera such that the driver/operator of thevehicle may request access from an individual, e.g. a security guard,who is remote from the entrance or facility 10. Additionally oralternatively, the access control apparatus may include a credentialreceiver (e.g., biometric scanner, numeric keypad, card reader, etc.)that may authenticate, authorize or verify a user device 24 or userthereof. The system 5 includes a remote server computer 50 configured tocommunicate with the movable barrier operator 40 over a network 52. Theremote server computer 50 may include one or more computers connected toprovide operability as discussed below.

The remote server computer 50 is also configured to communicate with oneor more sensors, indicated generally at 60. The sensors 60 may belocated at the perimeter barrier 12 of the facility 10. In oneembodiment, the sensors 60 communicate with the movable barrier operator40, which communicates sensor data to the remote server computer 50. Thecommunications between the sensors 60 and the movable barrier operator40 may include wired and/or wireless approaches. In one embodiment,signals are communicated between the particular sensor 60 and themovable barrier operator 40 via another device (e.g., a proxy or arouter).

The sensors 60 may be a presence detector that is configured to detectpresence of a vehicle 20. For example, the sensors 60 may include aphoto beam system 62 and/or a loop detector 64. Other presence sensors,indicated generally at 66, can include one or more of a passive infrareddetector, camera, a radio frequency receiver, a short-range (e.g.,Bluetooth) receiver, a magnetic detector, a light or sound-basedtime-of-flight sensor, a capacitance detector, sound detector, and anoptical detector (e.g., a camera). The sensors 60 may inform the movablebarrier operator 40 and/or the remote server computer 50 of the presenceof a vehicle 20 at the movable barrier 32 of the facility 10.

Referring to FIG. 2, the movable barrier operator 40 may include a motor70, a memory 72, and communication circuitry 74. The movable barrieroperator 40 may further include processing circuitry 76 that isoperatively coupled to one or more of the motor 70, the memory 72, andthe communication circuitry 74. The motor 70 is configured to beconnected to a movable barrier (e.g., movable barrier 32) to move themovable barrier between open and closed positions. The memory 72 maystore identification and security (e.g. rolling code) information forauthorized remote controls.

The communication circuitry 74 may be configured to receive wired and/orwireless communications from a local device (such as a local transmitteror local sensor) and/or a remote device (such as the remote servercomputer 50). In this way, the communication circuitry 74 may include aradio frequency signal receiver or transceiver 80 that may receive acommand signal from a radio frequency signal transmitter to change thestate of the movable barrier 32.

The communication circuitry 74 may further include a network interface82. The network interface 82 may be configured to communicate with theremote server computer 50 over the network 52, as shown in FIG. 1. Thenetwork interface 82 may communicate with the network 52 via wiredand/or wireless approaches, such as a wireless gateway or access point,e.g. a Wi-Fi router. The network interface 82 may receive a state changecommand from the remote server computer 50 (e.g., via the network 52) tocause the movable barrier operator 40 to change the state (e.g., aclosed position to an open position or vice versa) of the movablebarrier 32. The network interface 82 may also communicate information tothe remote server computer 50. Such information may include informationidentifying the vehicle 20, a user (e.g., driver and/or passenger)associated with the vehicle 20, the freight 22 of the vehicle 20,information pertaining to the movable barrier 32, information pertainingto one or more sensors 60 associated with the movable barrier 32, or anycombination thereof. The communication circuitry 74 may also include along-range wireless transceiver 83 that may communicate with otherdevices. For example, the communication circuitry may receivecommunications from one or more devices such as sensors having WiMax orLoRa-based communication operability, such as a V2X (vehicle toanything) sensor. Such sensors may be mounted, for example, to astoplight or stop sign at an intersection near the facility 10 and maydetect a beacon signal from the user device 24 or other component of thevehicle. The movable barrier operator 40 may thereby be able todetermine the vehicle 20 is nearby, and may further be able tocommunicate such information to the remote server computer 50.

The communication circuitry 74 may further includes a short-rangewireless transceiver 84. In one example, the short-range wirelesstransceiver 84 may be configured to receive a check-in signal directlyfrom the user device 24 over a short-range wireless protocol, such asBluetooth, near-field communication (NFC), or infrared. Thecommunication circuitry 74 may also include a wired communicationinterface 86 for communicating with one or more devices (e.g., a localsensor 60).

Referring to FIG. 3, the remote server computer 50 may facilitateoperation of one or more movable barrier operators 40 at the facility10. For example, the remote server computer 50 may communicate controlcommands (e.g., open, close, start, stop, etc.) to the movable barrieroperator 40 (see FIG. 1) of the facility 10. Additionally oralternatively, the remote server computer 50 may communicate controlcommands to one or more dock door operators 202 at the loading docks 14to operate associated loading dock doors 204, as discussed in greaterdetail below. To facilitate operation of the movable barrier operator40, the remote server computer 50 includes a network or communicationinterface 90 configured to communicate via the network 52 with movablebarrier operators 40 at the facility 10. The communication interface 90is further configured to communicate with the user device 24 via thenetwork 52.

The remote server computer 50 also includes a non-transitory,computer-readable medium such as a memory 92 for storing information.For example, the memory 92 may store facility information such asfacility identification, facility location, facility contactinformation, facility history information, etc. Schedule information,such as authorized arrival times and departure times for vehicles 20,may also be stored in the memory 92. The memory 92 may also storetransport logs, which may include actual arrival times and/or actualdeparture times, which are recorded when the user utilizes the userdevice 24 to operate the movable barrier operator 40. The ability of thesystem 5 to determine actual arrival and departure times based onoperation of the movable barrier operator provides independentverification and improved freight tracking accuracy over relying onpaper records. The memory 92 may also store barrier operatorinformation, which may include the times of operation of a given barrieroperator, a number of actuation events for a given barrier operator(e.g., lifetime actuation events, or actuation events since a lastmaintenance operation). The memory 92 may store information from thesensors 60 at a given facility 10 such as presence detections, times ofpresence detections, and/or estimated accuracy of detections. The memory92 may also store user information, which may include useridentification information, account information, contact information,user histories, still or moving images of the user, vehicle, etc.,and/or user notes. The memory 92 may further store freight informationsuch as freight identifiers, freight tracking information, freightnotes, bills of lading, and/or packaging slips. The memory 92 may alsostore loading dock information, such as the status of dock dooroperators 202, the position of a truck restraint 226 (see FIG. 5),height of a dock leveler 224, and/or identifications of sensors and/orconfigurable devices at a given loading dock.

The remote server computer 50 also includes a processor 94 that isoperatively coupled to the communication interface 90 and the memory 92.The processor 94 may determine whether a first condition is satisfied(e.g., whether the vehicle 20 has arrived at the facility 10), and mayfurther determine whether a second condition is satisfied (e.g., whetherthe vehicle 20 is authorized to access the facility 10 at that time), asdiscussed in greater detail below. Upon satisfaction of both conditions,the processor 94 may communicate a control command, via thecommunication interface 90, to an operator (e.g., movable barrieroperator 40 and/or dock door operator 202) at the facility 10 to operatea movable barrier. In other instances the remote server computer 50 may,alone or in conjunction with another apparatus, permit access to thefacility 10 based on satisfaction of a single condition or a pluralityof conditions. As another example, the remote server computer 50communicates a token to the user device 24 and the user device 24communicates a control command, including the token, to the movablebarrier operator 40 to cause the movable barrier operator 40 to changethe state of the movable barrier 32. Furthermore, the processor 94 maycommunicate a configuration command to effect a configuration of one ormore loading dock devices at the loading docks 14, as discussed ingreater detail with respect to FIG. 4.

The remote server computer 50 may take a variety of embodiments. Forexample, the remote server computer 50 may be an “off-site” servercomputer that is not located at the facility 10. In another embodiment,the remote server computer 50 is an “on-site” server computer that islocated at the facility 10. For example, the remote server computer 50may be located in an office of the facility 10.

Referring to FIG. 4, an example of the user device 24 for use by anoccupant of the vehicle 20 is shown. The user device 24 may include oneor more of a user input 100, such as a touch screen, keypad, speaker,microphone, heads-up display, augmented reality display, andcommunication circuitry 102 for communicating with a remote device(e.g., remote server computer 50). The communication circuitry 102 mayinclude a long-range wireless communication interface, such an interfacethat communicates with cellular networks (3G, 4G, 4G LTE, 5G), WiMaxnetworks, and/or LoRa networks as some examples. The communicationcircuitry 102 may also include a short-range wireless communicationinterface, such as an interface that communicates using Bluetooth,Wi-Fi, and/or ZigBee. The user device 24 may also include a memory 106,a power source 108 such as a battery or an electrical power source in avehicle, location circuitry 112 such as a global navigation satellitesystem (e.g., GPS) transceiver, and an optical device 116 such as acamera and/or a barcode scanner. The user device 24 may further includea processor circuit 118 operatively coupled to the other components ofthe user device 24 for controlling the operation thereof.

In one aspect, the user device 24 may be a personal user device, such asa smartphone, tablet computer, personal computer, or wearable device(e.g., smartwatch). As another example, the user device 24 is avehicle-integrated user device, such as a human machine interface of thevehicle 20. Examples of human machine interfaces include a vehiclecenter stack, a dashboard display, a navigation unit, a telematics unit,an infotainment unit, and a heads-up display system.

Referring again to FIG. 1, an arrival or check-in process will now bedescribed. Upon arriving at the facility 10 (e.g., at the perimeterbarrier 12 of the facility 10), at least a portion of a check-in processmay be performed at the user device 24. During the check-in process, acheck-in communication 130 is transmitted from the user device 24 to theremote server computer 50 via the network 52. According to one aspect,the check-in process is initiated when a user, such as the vehicleoperator, opens and/or controls an application of the user device 24.For example, the vehicle occupant may provide an input at the user input100, which may include a touch screen, to request a change of state ofthe movable barrier 32. The processor circuit 118 is configured to causethe communication circuitry 102 to communicate the check-incommunication 130 to the remote server computer 50. In this way, theuser may manually effect transmission of the check-in communication 130from the user device 24 upon arriving at the facility 10.

According to another aspect, the user device 24 may automatically effecttransmission of the check-in communication 130 from the user device 24.In this aspect, transmission of the check-in communication 130 may beeffected in response to the processor circuit 118 determining (e.g., vialocation circuitry 112) that the user device 24 is at a predeterminedgeolocation or proximity relative to the facility 10 (e.g., at themovable barrier 32). As another example, the user device 24 mayautomatically effect transmission of the check-in communication upon theuser device 24 receiving a beacon signal or light pattern from themovable barrier operator 40 or, as previously mentioned, an accesscontrol apparatus that is associated or in communication with themovable barrier operator 40.

In one embodiment, the check-in communication 130 is communicateddirectly to the remote server computer 50 via the network 52. In anotherapproach, the check-in communication 130 is communicated to the movablebarrier operator 40 (via signal 138), which relays the check-incommunication 130 to the remote server computer 50 via the network 52.In such an approach, the movable barrier operator 40 may function as aterminal for relaying information (e.g., check-in information) to theremote server computer 50.

The check-in communication 130 may include location information. Forexample, the check-in communication 130 may include a locationassociated with the vehicle 20 (e.g., as informed by the locationcircuitry 112 of the user device 24). Additionally or alternatively, thecheck-in communication 130 may include a location of a movable barrier32 or movable barrier operator 40 associated with the location of thevehicle 20.

Additionally or alternatively, the check-in communication 130 mayinclude a check-in identifier. The check-in identifier may includeinformation pertaining to at least one of the user, the vehicle 20, theuser device 24, and freight 22 transported (or to be transported) by thevehicle 20. Information pertaining to the user may include a useridentifier (e.g., name, employer, user ID). Information pertaining tothe vehicle 20 may include a vehicle identifier (which may include atractor identifier and/or a trailer identifier), vehicle ownerinformation, vehicle schedule information (e.g., prior scheduleinformation and/or future schedule information), and/or vehiclecharacteristic. A vehicle characteristic may include, for example, aheight of the vehicle 20, a height and/or type of a rear impact guard ofthe vehicle 20, and/or an identifier associated with the vehicle 20.Information pertaining to the user device 24 may include a globallyunique ID of the user device 24. Freight-related information may includea name and/or address of the shipper, a name and/or address of therecipient, dates (e.g., pickup and/or delivery dates), locations (e.g.,pickup and/or delivery locations), purchase orders or reference numbers,description of the freight (e.g., number of shipping units, dimensions,weight, materials, packaging, freight class, hazardous materialdesignation, storage requirements such as temperature or environmentalrequirements, etc.), instructions, or combinations thereof. Otherfreight-related information may include stock keeping unit (SKU) and/orfood lot numbers.

The check-in communication 130 may include information relating to imagedata such as one or more of pictures or video captured, for example, bya sensor 60 or by the optical device 116 of the user device 24. Thepictures and/or video may include pictures and/or video of an identifierof the vehicle 20 such as a trailer number, a license plate, a barcodeof the trailer, the user driver's license, a bill of lading, and/orfreight 22 transported (or to-be-transported) by the vehicle 20.

The user device 24 may receive the information for the check-inidentifier in a number of ways. For example, the user may open anapplication on the user device 24 and enter a user name and passwordusing the user interface 100. The user device 24 has stored thereon orretrieves from the remote server computer 50 profile information for theuser such as driver's license number, trucking company, and insuranceinformation as some examples. When the vehicle 20 picks up a trailer ata first location to deliver to the facility 10, the user device 24receives a digital bill of lading and/or packing slip from the firstlocation which includes freight information (e.g., SKUs, lot numbers,pallet numbers). The user utilizes the optical device 116 of the userdevice 24 to take a picture of a trailer number, barcode, or othermachine-readable indicium of the trailer. The picture evidences that theuser is actually picking up the trailer. The user device 24 communicatesthe received information to the remote server computer 50, such as oncethe vehicle 20 leaves the remote facility, during transit to thefacility 10, and/or upon arrival at the facility 10. The user device 24may also provide information to the remote server computer 50 duringtravel, such as location data, which permits real-time tracking of thevehicle 20.

In some embodiments, the freight information received by the user device24 may be directly communicated to the remote server computer 50.Alternatively or additionally, the freight information may be recordedusing a digital distributed ledger system, e.g., private blockchain. Theremote server computer 50 and/or distributed ledger may maintain adetailed record of each shipped product as the product travels fromfacility to facility and eventually to a point of sale (as an example).The detailed record facilitates accurate supply chain tracking andtraceability, such as for product recalls.

As discussed, the check-in communication 130 may be transmitted toremote server computer 50 via the network 52. Upon receiving thecheck-in communication 130, the remote server computer 50 performs anauthorization check based at least in part on the check-in identifier.For example, the remote server computer 50 may determine whether thevehicle 20 is authorized to access the facility 10. The determinationmay include determining whether the user, vehicle 20, and/or user device24 are authorized to access the facility 10; for example, within aparticular date range, on a particular day, within a particular timerange, and/or at a particular time.

In one example, the check-in communication 130 includes a vehicleidentifier, and the memory includes a schedule indicating a particulartime that the vehicle 20 is authorized to arrive at the facility 10. Inthis example, the remote server computer 50 may determine whether thevehicle 20 is authorized to access the facility 10 at the time of thecheck-in communication 130. If the vehicle 20 is not authorized toaccess the facility 10 at the time of the check-in communication 130,the remote server computer 50 may communicate with the user device 24 toinform the vehicle occupant that the vehicle 20 is not authorized toaccess the facility 10 at that time. The communication with the userdevice 24 may further inform the vehicle occupant of the time (or rangeof times) that the vehicle 20 is authorized to access the facility 10.

If the vehicle 20 is not authorized to access the facility 10, such asif there are no open loading docks, the remote server computer 50 maycommunicate an instruction to the user via the user device 24 to parkthe trailer of the vehicle 20 outside of the facility. This may occur,for example, if the user is delivering a trailer to the facility 10outside of normal business hours.

At the time of the check-in communication 130, the remote servercomputer 50 may perform a presence verification process. For example,the remote server computer 50 may communicate with one or more sensors60 at the facility 10 to verify the vehicle 20 has arrived at thefacility 10.

In one embodiment, the remote server computer 50 may communicate withthe movable barrier operator 40 for verification of vehicle presence atthe movable barrier 32. The movable barrier operator 40 may be informedof a presence of the vehicle 20 at the movable barrier 32 throughvarious approaches. In one approach, the movable barrier operator 40communicates with one or more sensors 60 located at the movable barrier32 of the facility 10. As such, the sensors 60 may report the detectedpresence of the vehicle 20 to the movable barrier operator 40.

In one example, verification of the presence of the vehicle 20 mayinclude detecting a break in an optical beam transmitted by a photo beamsystem 62 that is in communication with the movable barrier operator 40,as indicated by signal 132. In another example, verification of thepresence of the vehicle 20 may include detecting a change in the basefrequency of an electrical signal transmitted by a loop detector 64 thatis in communication with the movable barrier operator 40, as indicatedat signal 134. The one or more sensors 60 may include other sensors 66that are in communication with the movable barrier operator 40, asindicated at signal 136, may be used for detecting the presence of thevehicle 20 at the movable barrier 32. As discussed, such sensors 66 mayinclude one or more of a passive infrared detector, a radio frequencyreceiver, a short-range (e.g., Bluetooth) receiver, a magnetic detector,a capacitance detector, a time-of-flight sensor, sound detector, and anoptical detector (e.g., a camera).

In another approach, the movable barrier operator 40 is configured todirectly detect a presence of a vehicle 20. For example, thecommunication circuitry 74 of the movable barrier operator 40 maycommunicate with the user device 24, as indicated at signal 138. Suchcommunication may be, for example, via a short-range (e.g., Bluetooth)protocol.

The sensors 60 inform the movable barrier operator 40 of a presence orabsence of a vehicle 20 at the perimeter barrier 12. The movable barrieroperator 40 is configured to transmit a verification communication 140to the remote server computer 50. The verification communication 140 mayinclude, for example, information identifying the movable barrieroperator 40 such as device ID, gate ID, and/or location (e.g., streetname, latitude and longitude). The verification communication 140 mayalso include information detected by the sensors 60, such as anidentification number or barcode of the trailer and/or tractor.

In still another embodiment, one or more of the sensors 60 maycommunicate a verification communication to the remote server computer50 (e.g., via the network 52). For example, as shown in FIG. 1, a sensor66 may communicate a verification communication 140′ to the remoteserver computer 50. Additionally or alternatively, one or both of thephoto beam system 62 and the loop detector 64 may communicate averification communication to the remote server computer 50. In thismanner, one or more of the sensors 60 may include a long-range wirelesscommunication interface and/or a wired communication interface.

In one approach, the one or more sensors 60 may continuously orperiodically monitor for the presence of a vehicle 20. In anotherapproach, the one or more sensors 60 may enter a “sleep” mode, and maycheck for the presence of a vehicle 20 in response to a “wake” signaltransmitted from the movable barrier operator 40, the remote servercomputer 50, and/or the user device 24. For example, the movable barrieroperator 40 may be configured to transmit a wake signal to the sensor 60in response to the movable barrier operator 40 receiving a vehiclepresence query from the remote server computer 50.

The various approaches described herein allow for the remote servercomputer 50 to be informed of a presence or absence of a vehicle 20 atthe movable barrier 32 of a facility 10. For example, the remote servercomputer 50 may receive an affirmative indication (e.g., viaverification communication 140, 140′) of a presence of the vehicle 20,or an affirmative indication of the absence of the vehicle 20 (e.g., asreported by a sensor 60 that does not detect the vehicle 20).Additionally or alternatively, the remote server computer 50 may inferan absence of the vehicle 20 in response to not receiving a verificationcommunication 140, 140′.

Upon the remote server computer 50 determining the check-in identifierof the check-in communication 130 indicates authorization of the vehicle20 to access the facility 10, and after receiving the verificationcommunication 140, 140′, the remote server computer 50 is configured tocause the movable barrier operator 40 to move the movable barrier 32between the closed position (shown in FIG. 1) to an open positionwhereby the vehicle 20 may pass into the secured premises 16. The remoteserver computer 50 may cause the movable barrier operator 40 to move themovable barrier 32 by communicating a control command to the movablebarrier operator 40. The “entrance time,” which corresponds to themovable barrier operator 40 moving the movable barrier 32 between closedand open positions, may be stored in a memory at one or both of themovable barrier operator 40 (memory 72) and the remote server computer50 (memory 92). The entrance time may be utilized as an electronicsignature to check in (entry) and check out (exit) a vehicle 20 from ageographic location, facility gate, and/or dock.

Further, the entrance time recorded at the memory 72, 92 provides anindependently obtained time the vehicle 20 entered the facility 10 whichimproves the accuracy of tracking movement of the vehicle 20. The remoteserver computer 50 may communicate a notification to a manager ormanagement computer system of the facility 10 that indicates the vehicle20 has entered at the movable barrier 32. The manager or managementcomputer system may quickly assign staff to prepare to unload and/orload the vehicle 20.

The check-in process and the presence verification process, includingoperations thereof, may be performed in any suitable order. As such, theremote server computer 50 may cause the movable barrier operator 40 tomove the movable barrier 32 in response to receiving the verificationcommunication 140, 140′ after having previously received the check-incommunication 130. In another example, the remote server computer 50 maycause the movable barrier operator 40 to move the movable barrier 32 inresponse to receiving the check-in communication 130 after havingpreviously received the verification communication 140, 140′. In thelatter approach, the remote server computer 50 may continuously orperiodically receive a verification communication 140, 140′ such thatthe remote server computer 50 is aware of the presence of the vehicle 20at the movable barrier 32 prior to receiving the check-in communication130 from the user device 24.

The remote server computer 50 may receive confirmation of passage of thevehicle 20 through the opened movable barrier 32. For example, photobeam system 62, which previously had an interrupted photo beam while thevehicle 20 was positioned outside of the movable barrier 32, may reporta series of interruptions as the wheels of the vehicle 20 travel throughthe photo beam. In another example, a forward photo beam system 62′,which previously had an uninterrupted photo beam while the vehicle 20was positioned outside of the perimeter barrier 12, may report aninterrupted photo beam. As another example, the sensor 60 may include acamera having image recognition operability to detect the vehicle 20entering the facility 10.

Prior to, after, or concurrent with the opening of the movable barrier32, the remote server computer 50 may communicate a loading dockidentification to the user device 24 (e.g., to the communicationcircuitry 102 of the user device 24). The loading dock identificationmay identify a particular loading dock from among the plurality ofloading docks 14. For example, the loading dock identifier may instructthe vehicle occupant to direct the vehicle 20 to “Dock 3” of thefacility 10, as indicated at arrow 150. Alternatively or additionally,the loading dock identification may include navigation information, suchas turn-by-turn directions or a map, for the user device 24 to presentto the user.

In one embodiment, a particular loading dock may be selected based atleast in part on dock availability. For example, “Dock 3” may be theonly available loading dock or is the only loading dock with necessaryspace availability. Alternatively or additionally, a particular loadingdock may be selected based at least in availability of at least one ofstaff and equipment (e.g., hazardous or cold storage).

In another embodiment, a particular loading dock may be selected basedat least in part on freight to be delivered by the vehicle 20 or pickedup by the vehicle 20. For example, “Dock 3” is the only loading dockequipped to handle hazardous material, or has the capability for storingthe freight in the necessary storage environment (temperature, humidity,etc.). In another aspect, a particular loading dock may be selectedbased at least in part on dock personnel at the facility 10, e.g., dockworkers are available at “Dock 3” but not at “Dock 1”. In anotheraspect, a particular loading dock may be selected based at least in parton loading dock accessories, e.g., a dock leveler is provided at “Dock3” but not at “Dock 2”. In another aspect, a particular loading dock maybe selected based at least in part on usage patterns of the plurality ofloading docks. For example, the dock door operator associated with “Dock3” may have a fewer number of operation events, e.g., “open” or “close,”than the dock door operator associated with “Dock 4.” In another aspect,a particular loading dock may be selected based at least in part on amaintenance schedule of the plurality of loading docks. For example,“Dock 1” may be scheduled for maintenance while the vehicle 20 isexpected to be at the facility 10, so use “Dock 3” instead. Informationused to assign a particular loading dock may be determined, for example,from a bill of lading or vehicle information (e.g., trailer number) thatwas communicated during the check-in process.

If no loading dock is available, but the vehicle 20 is permitted toenter the facility 10, the remote server computer 50 may transmit aninstruction to the user device 24 instructing the user to drive thevehicle 20 to a waiting area 160.

Referring now to FIG. 5, a loading dock area 200 (which may correspondto a loading dock 14 of FIG. 1) includes a dock door operator 202 thatis configured to be operatively connected to a loading dock door 204 tomove the loading dock door 204 between a closed position and an openposition. The loading dock door 204 shown in FIG. 5 is in the form of aroller door. In other aspects, the loading dock door 204 may be in theform of a paneled door, a swinging door, a gate, or other suitablebarrier for controlling access to an interior 206 of the loading dockarea 200.

The dock door operator 202 may include components that are similar tothe components of the movable barrier operator 40 discussed with respectto FIG. 2. For example, the dock door operator 202 includes a motor,communication circuitry, a memory, and a processor. The dock dooroperator 202 is configured to communicate via communication circuitrythereof with the remote server computer 50 over the network 52.

The loading dock area 200 may include one or more loading dockcomponents, indicated generally at 210. Example loading dock components210 include a photo beam system 220 including an emitter 222, a safetyedging of the door 204, a dock leveler 224, a vehicle restraint 226(e.g., a trailer lock), an exterior camera 228, an interior camera 230,edge guards or dock seal 232, dock bumper 234, an optical detector 236(e.g., a camera or light time-of-flight sensor), a sensor 238 (e.g., apassive infrared (PIR), ultrasonic, and/or microwave sensor), and a loopdetector 240. One or more of the loading dock components 210 may be incommunication (e.g., wired or wireless communication) with one or bothof the dock door operator 202 and a gateway device 250. The gatewaydevice 250 may be a communications hub that is in communication with thevarious loading dock components 210 and one or both of the dock dooroperator 202 and the remote server computer 50, but is not configured tomove the loading dock door 204.

In one embodiment, the remote server computer 50 may send a controlcommand to the dock door operator 202 and/or the gateway device 250 toconfigure at least one component of the loading dock components 210 tofacilitate receiving the vehicle 20 at the loading dock area 200. Such acontrol or configuration command may be issued, for example, upon theconclusion of one or both of the check-in process and the presenceverification process, and/or upon the remote server computer 50 causingthe movable barrier operator 40 to move the movable barrier 32.

The one or more of the loading dock components 210 may be configuredbased at least in part on at least one characteristic of the vehicle 20.In one example, the remote server computer 50 may communicate a controlcommand to cause a height adjustment of the dock leveler 224. The heightadjustment may be based on a known height of a floor of the trailerassociated with the vehicle 20 (e.g., as indicated by the check-incommunication 130). In this way, the dock leveler 224 may provide anappropriate transition from a floor of the interior 206 of the loadingdock area 200 to the load space associated with the vehicle 20. In stillanother example, the remote server computer 50 may communicate a controlcommand to cause an adjustment of the operation of the vehicle restraint226, such as adjusting an orientation of a vehicle restraint hook oradjusting automated wheel chocks. As an example, the control command maycause an actuator to shift a carriage of the vehicle restraint 226 up ordown along a vertical track of the vehicle restraint 226. When thecarriage has been shifted to the height requested by the controlcommand, the hook of the vehicle restraint 226 is positioned to pivot upand over the rear impact guard of the vehicle 20 to secure the vehicle20 at the loading dock.

Upon the vehicle 20 arriving at the particular loading dock area 200, a“dock arrival” process is performed. More particularly, the remoteserver computer 50 may receive (e.g., at the communication interface 90)a dock arrival communication 260 from the user device 24 indicatingarrival of the vehicle 20 at the particular loading dock area 200. Inone embodiment, the dock arrival communication 260 is transmitted when avehicle occupant opens and/or controls an application of the user device24 via the user input 100 (e.g., via a touch screen). In this way, thevehicle occupant may manually effect transmission of the dock arrivalcommunication 260 from the user device 24 upon arriving at the loadingdock area 200. According to another aspect, the user device 24 mayautomatically effect transmission of the dock arrival communication 260.In this aspect, transmission of the dock arrival communication 260 maybe effected in response to the processor circuit 118 determining (e.g.,via location circuitry 112) that the user device 24 is at apredetermined geolocation or proximity relative to the loading dock area200 (e.g., proximate the loading dock door 204). In one approach, thedock arrival communication 260 is communicated to the remote servercomputer 50 via the network 52. In another approach, the dock arrivalcommunication 260 is communicated to the dock door operator 202 and/orthe gateway device 250 for communication to the remote server computer50 via the network 52.

Upon receiving the dock arrival communication 260, the remote servercomputer 50 may perform a dock presence verification process. Moreparticularly, the remote server computer 50 may communicate (e.g., viathe communication interface 90) with one or more devices at the loadingdock area 200 to verify the vehicle 20 has arrived at the loading dockarea 200.

In one aspect, the remote server computer 50 may communicate with thedock door operator 202 for verification of vehicle presence at theloading dock area 200. The dock door operator 202 and/or the gatewaydeice 250 may be informed of a presence of the vehicle 20 at the loadingdock area 200 through various approaches. In one approach, the dock dooroperator 202 and/or the gateway device 250 communicates with one or moreof the loading dock components 210.

In one example, verification of the presence of the vehicle 20 mayinclude detecting a break in an optical beam transmitted by a photo beamsystem 220. In another example, verification of the presence of thevehicle 20 may include detecting a change in the base frequency of theelectrical signal transmitted by the loop detector 240. Other sensorsand loading dock components 210, discussed above, may be used fordetecting the presence of the vehicle 20 at the loading dock area 200.

In another approach, the dock door operator 202 is configured todirectly detect a presence of a vehicle 20 at the loading dock area 200.For example, the communication circuitry of the dock door operator 202may communicate with the user device 24, as indicated at signal 262.Such communication may be, for example, via a short-range protocol(e.g., Bluetooth).

As such, at least one of the dock door operator 202 and the gatewaydevice 250 is informed of a presence (or absence as informed orinferred) of a vehicle 20 at the loading dock area 200. In one aspect,the dock door operator 202 is configured to transmit a dock verificationcommunication 264 to the remote server computer 50. The dockverification communication 264 may be transmitted in response to, forexample, the dock door operator 202 receiving a presence indication froma loading dock component 210 or the user device 24, or in response toreceiving a signal 266 from the gateway device 250. Additionally oralternatively, the gateway device 250 may transmit a dock verificationcommunication 268 to the remote server computer 50.

In still another aspect, one or more of the loading dock components 210may communicate a verification communication to the remote servercomputer 50 independently of the dock door operator 202 and gatewaydevice 250 (e.g., via the network 52). In this way, a loading dockcomponent 210 may include a wired or wireless network interface.

In one approach, a loading dock component 210 may continuously orperiodically monitor for the presence of a vehicle 20. In anotherapproach, the loading dock component 210 may enter a “sleep” mode, andmay check for the presence of a vehicle 20 in response to a “wake”signal transmitted from the dock door operator 202, the gateway device250, the remote server computer 50 (e.g., as part of the presenceverification process), and/or the user device 24. For example, the dockdoor operator 202 or gateway device 250 may be configured to transmit awake signal to the loading dock component 210 in response to receiving avehicle presence query from the remote server computer 50.

The various approaches described herein allow for the remote servercomputer 50 to be informed of a presence of a vehicle 20 at the loadingdock area 200. Upon the remote server computer 50 receiving the dockarrival communication 260 from the user device 24 and a dockverification communication 264 from the dock door operator 202 and/or adock verification communication 268 from the gateway device 250, theremote server computer 50 may be configured to cause the dock dooroperator 202 to move the loading dock door 204 from a closed position toan open position whereby access to the interior 206 of the loading dockarea 200 is achieved. The remote server computer 50 may cause the dockdoor operator 202 to move the loading dock door 204 by communicating acontrol command to the dock door operator 202. Furthermore, the remoteserver computer 50 may receive, from the dock door operator 202, anindication of the dock door operator 202 moving the loading dock door204 between closed and open positions. The “open time,” whichcorresponds to the dock door operator 202 moving the loading dock door204 between a closed and an open position, may be stored in a memory atone or both of the dock door operator 202 (memory 72) and the remoteserver computer 50 (memory 92). The open time recorded for the operationof the dock door operator 202 may be utilized as an electronic signaturethat permits the system 5 to independently verify the vehicle 20 is atthe loading dock 14.

In one approach, the remote server computer 50 may further be configuredto store, in the memory 92, a “close time” that corresponds to the dockdoor operator 202 moving the loading dock door 204 between an open and aclosed position. The close time may be indicative of the vehicle 20leaving the loading dock area 200. Furthermore, the remote servercomputer 50 may be configured to store, in the memory 92, a “departuretime” that corresponds to the movable barrier operator 40 moving themovable barrier 32 of the facility 10 between a closed position and anopen position to permit the vehicle 20 to exit the facility 10. Thedeparture time may be indicative of the vehicle 20 leaving the facility10 via the movable barrier 32 and may provide an electronic signaturethe system 5 may use to independently track movement of the vehicle 20and freight therein. In this way, arrival, duration of stay, anddeparture times for a particular vehicle 20 or particular freighttransport may be logged and maintained. Such information may beinformative of the shipping/receiving performance of the facility and/ortimeliness/efficiency of the transportation carrier or vehicledriver/operator, and useful at least in part to determine whether feesor charges are to be assessed e.g. for detention, etc.

As part of the check out process, the remote server computer 50 mayinitiate freight billing and/or initiate a completed bill of lading. Thecheck out process may involve providing freight information, such as anew or updated bill of lading, for the products loaded onto the vehicle20 at the facility 10 to the remote server computer 50 and/or userdevice 24. The new freight information is associated with the user'sprofile until the user has delivered the freight to the assignedfacility. Alternatively or additionally, the check out process mayinvolve the remote server computer 50 generating a notification that thedriver is available to pickup a new freight load.

In one aspect, the remote server computer 50 may transmit one or morenotifications to a computing device (e.g., a desktop, laptop,smartphone, or tablet) at the facility 10 reporting the activity of thevehicle 20 or various components of the facility 10. Such reportingnotifications may be transmitted during the “check-in” process and/orduring the “dock arrival” process. For example, the remote servercomputer 50 may transmit reporting notifications in response toreceiving the check-in communication 130 (such that personnel at thefacility 10 are notified of the arrival of the vehicle 20 at the movablebarrier 32), in response to receiving the verification communication140, 140′, in response to commanding the movable barrier operator 40 tomove the movable barrier 32, and/or in response to a sensor 60confirming the vehicle has entered the secured premises 16. The remoteserver computer 50 may also or may instead transmit reportingnotifications in response to receiving the dock arrival communication260 (such that personnel at the facility 10 are notified of the arrivalof the vehicle 20 at the loading dock area 200), in response toreceiving a dock verification communication 264, 268, and/or in responseto commanding the dock door operator 202 to move the loading dock door204.

Referring now to FIG. 6, a method 300 for controlling access to afacility including a movable barrier (e.g., movable barrier 32) and aplurality of loading docks (e.g., loading docks 14) is described. One ormore of the steps described with respect to method 300 may occur at, ormay be performed by, one or more of the remote server computer 50,movable barrier operator 40, dock door operator 202, gateway device 250,and the user device 24.

The method 300 includes receiving 302, from a user device (e.g., userdevice 24) associated with a vehicle (e.g., vehicle 20), a check-incommunication that includes a check-in identifier. The check-inidentifier may indicate at least one characteristic of the vehicle, auser of the user device, the user device, and/or freight in the vehicle.The at least one characteristic of the vehicle may relate to, forexample, a height of the vehicle or to a configuration of a rear impactguard of the vehicle.

The method 300 further includes receiving 304 a verificationcommunication that verifies a presence of the vehicle relative to asensor (e.g., sensor 60) associated with the movable barrier.

The method 300 further includes causing 306 a movable barrier operator(e.g., movable barrier operator 40) associated with the movable barrierto move the movable barrier between closed and open positions inresponse to the check-in identifier indicating authorization to accessthe facility and in response to receiving the verificationcommunication.

The method 300 further includes selecting 308 a particular loading dockfrom the plurality of loading docks. The method 300 further includescommunicating 310 a loading dock identification representative of theparticular loading dock to the user device to direct the vehicle to theparticular loading dock.

In one embodiment, the method 300 may further include causing theparticular loading dock to configure at least one component of theparticular loading dock, according to the at least one characteristic ofthe vehicle to facilitate receiving the vehicle at the particularloading dock. For example, the method 300 may include adjusting a heightof a leveler of the particular loading dock or adjusting the position ofa restraint of the particular loading dock.

The approaches described herein may promote efficiency in variousaspects of the operation of the facility 10. For example, because thefacility 10 may be notified of the arrival of a vehicle 20 prior to thevehicle 20 entering the facility 10, facility personnel may assign andprepare the loading dock 14 in advance of the vehicle 20 arriving at theloading dock 14. This may reduce delays in initiating a loading orunloading process at the loading dock 14. Furthermore, a check-inprocess may be performed at any time of day such that a vehicle operatormay deliver and drop off a trailer to the facility 10 outside of typicalbusiness hours. Furthermore, performance of both vehicle users andfacilities may be logged and monitored over time. Still further, becausethe remote server computer 50 may store freight information provided bycheck-in communications 130, the approaches described herein may provideincreased traceability of freight.

While there have been illustrated and described particular embodimentsof the present invention, it will be appreciated that numerous changesand modifications will occur to those skilled in the art, and it isintended for the present invention to cover all those changes andmodifications which fall within the scope of the appended claims. It isintended that the phrase “at least one of” as used herein be interpretedin the disjunctive sense. For example, the phrase “at least one of A andB” is intended to encompass only A, only B, or both A and B.

What is claimed is:
 1. A method for controlling access to a facilityincluding a movable barrier and a plurality of loading docks, the methodcomprising: receiving, from a user device associated with a vehicle, acheck-in communication that includes a check-in identifier; receiving averification communication that verifies a presence of the vehiclerelative to a sensor associated with the movable barrier; causing amovable barrier operator associated with the movable barrier to move themovable barrier between closed and open positions in response to thecheck-in identifier indicating authorization to access the facility andin response to receiving the verification communication; selecting aparticular loading dock from the plurality of loading docks; andcommunicating a loading dock identification representative of theparticular loading dock to the user device to direct the vehicle to theparticular loading dock.
 2. The method of claim 1 wherein the check-inidentifier indicates at least one characteristic of the vehicle; andcausing the particular loading dock to configure at least one componentof the particular loading dock, according to the at least onecharacteristic, to receive the vehicle.
 3. The method of claim 2 whereinthe at least one characteristic of the vehicle includes a height of thevehicle, and wherein causing the particular loading dock to configurethe at least one component of the particular loading dock to receive thevehicle includes adjusting a height of a leveler of the particularloading dock.
 4. The method of claim 2 wherein the at least onecharacteristic of the vehicle relates to a rear impact guard of thevehicle, and wherein causing the particular loading dock to configurethe at least one component of the particular loading dock to receive thevehicle includes adjusting operation of a restraint of the particularloading dock.
 5. The method of claim 1 further comprising causing a dockdoor operator associated with the particular loading dock to move a dockdoor of the particular loading dock between closed and open positions.6. The method of claim 1 wherein selecting the particular loading dockfrom the plurality of loading docks includes selecting the particularloading dock from the plurality of loading docks based at least in parton usage patterns of the plurality of loading docks.
 7. The method ofclaim 1 further comprising: receiving, from the user device, a dockarrival communication indicating arrival of the vehicle at theparticular loading dock; receiving, from a sensor of the particularloading dock, a dock verification communication confirming arrival ofthe vehicle at the particular loading dock; and causing a dock dooroperator associated with the particular loading dock to move a dock doorof the particular loading dock between closed and open positions uponreceipt of the dock arrival communication and receipt of the dockverification communication.
 8. The method of claim 1 further comprisingdetermining at least one of whether the check-in identifier indicatesauthorization to access the facility, and determining whether thecheck-in identifier indicates authorization to access the facility at aparticular time.
 9. The method of claim 1 further comprising receiving afreight identifier associated with the vehicle; and wherein causing themovable barrier operator associated with the movable barrier to move themovable barrier between closed and open positions includes causing themovable barrier operator to move the movable barrier in response to thefreight identifier indicating authorization to enter into the facility.10. The method of claim 1 further comprising: storing, in a memory, anentrance time corresponding to the movable barrier operator moving themovable barrier between closed and open positions; receiving, from adock door operator of the particular loading dock, an indication of thedock door operator moving a dock door of the particular loading dockbetween closed and open positions; and storing, in the memory, a dockoperation time corresponding to the dock door operator moving the dockdoor between the closed and open positions.
 11. The method of claim 1wherein causing the movable barrier operator to move the movable barrierbetween closed and open positions includes communicating a controlcommand to the movable barrier operator to cause the movable barrieroperator to move the movable barrier between closed and open positions.12. An apparatus for facilitating access to a facility having a movablebarrier and a plurality of loading docks, the apparatus comprising: acommunication interface configured to receive a check-in communicationfrom a user device associated with a vehicle, the communicationinterface further configured to receive a verification communicationthat verifies a presence of the vehicle relative to a sensor associatedwith the movable barrier; a processor circuit operatively coupled to thecommunication interface, the processor circuit configured to: cause amovable barrier operator associated with the movable barrier to move themovable barrier between closed and open positions in response to thecheck-in communication indicating authorization to access the facilityand in response to receiving the verification communication; select aparticular loading dock from the plurality of loading docks; andcommunicate a loading dock identification representative of theparticular loading dock to the user device to direct the vehicle to theparticular loading dock.
 13. The apparatus of claim 12 wherein thecommunication interface is configured to receive a vehicleidentification indicating at least one characteristic of the vehicle;and wherein the processor circuit is configured to cause the particularloading dock to configure at least one component of the particularloading dock to receive the vehicle based at least in part on the atleast one characteristic of the vehicle.
 14. The apparatus of claim 13wherein the at least one characteristic includes a height of thevehicle; and the processor circuit is configured to cause the particularloading dock to configure the at least one component of the particularloading dock to receive the vehicle by adjusting a height of a levelerof the particular loading dock.
 15. The apparatus of claim 13 whereinthe at least one characteristic of the vehicle relates to a rear impactguard of the vehicle; and the processor circuit is configured to causethe particular loading dock to configure the at least one component ofthe particular loading dock to receive the vehicle by adjustingoperation of a restraint of the particular loading dock.
 16. Theapparatus of claim 12 further comprising a memory configured to storeusage patterns of the plurality of loading docks; and wherein theprocessor circuit is configured to select the particular loading dockbased at least in part on the usage patterns of the plurality of loadingdocks.
 17. The apparatus of claim 12 wherein the communication interfaceis configured to receive, from the user device, a dock arrivalcommunication indicating arrival of the vehicle at the particularloading dock; wherein the communication interface is configured toreceive, from a sensor of the particular loading dock, an arrivalconfirmation communication confirming arrival of the vehicle at theparticular loading dock; and wherein the processor circuit is configuredto permit a dock door operator to move a dock door of the particularloading dock between closed and open positions upon receipt of the dockarrival communication and receipt of the arrival confirmationcommunication.
 18. The apparatus of claim 12 wherein the processorcircuit is configured to determine whether the check-in communication isauthorized to access the facility based at least in part on whether theuser device is requesting access to the facility during an authorizedtime period.
 19. The apparatus of claim 12 wherein the communicationinterface is configured to receive a freight identifier associated withthe vehicle; and wherein the processor circuit is configured to permitthe movable barrier operator to move the movable barrier between closedand open positions in response to the freight identifier being permittedentry into the facility.
 20. The apparatus of claim 12 wherein theprocessor circuit is configured to: store, in a memory, an entrance timecorresponding to the movable barrier operator moving the movable barrierbetween closed and open positions; receive, from a dock door operator ofthe particular loading dock, an indication of the dock door operatormoving a dock door of the particular loading dock between closed andopen positions; and store, in the memory, a dock operation timecorresponding to the dock door operator moving the dock door between theclosed and open positions.
 21. The apparatus of claim 12 wherein theprocessor circuit is configured to permit the movable barrier operatorto move the movable barrier between closed and open positions bycommunicating a control command to the movable barrier operator to causethe movable barrier operator to move the movable barrier between closedand open positions.
 22. A user device comprising: a user interface;communication circuitry configured to communicate with a remotecomputer; and a processor circuit operatively coupled to the userinterface and the communication circuitry, the processor circuitconfigured to cause the communication circuitry to communicate acheck-in communication for a vehicle to the remote computer, thecheck-in communication configured to cause the remote computer to permita movable barrier operator of a facility to change a state of anassociated movable barrier in response to the check-in communicationindicating authorization to access the facility and in response toreceipt by the remote computer of a verification communication from asensor associated with the movable barrier verifying a presence of thevehicle relative to the movable barrier; the communication circuitryfurther configured to receive, from the remote computer, a loading dockidentification representative of a particular loading dock from aplurality of loading docks of the facility; and the processor circuitfurther configured to cause the user interface to provide a usercommunication indicative of the particular loading dock.
 23. The userdevice of claim 22 wherein the check-in communication includes at leastone characteristic of the vehicle, the check-in communication configuredto cause the remote computer to configure at least one component of theparticular loading dock to receive the vehicle.
 24. The user device ofclaim 22 wherein the check-in communication includes at least one of alocation of the vehicle and a location of the movable barrier operator.25. The user device of claim 22 wherein the processor circuit isconfigured to cause the communication circuitry to communicate a dockarrival communication to the remote computer.
 26. The user device ofclaim 22 wherein the user communication indicative of the particularloading dock includes navigation information to direct the vehicle tothe particular loading dock.
 27. The user device of claim 22 wherein theuser interface is configured to receive a user input requesting themovable barrier operator to change a state of the movable barrier; andthe processor circuit is configured to cause the communication circuitryto communicate a control command to the movable barrier operator thatcauses the movable barrier operator to change the state of the movablebarrier.